Continuous data protection with cloud resources

ABSTRACT

In one aspect, a method includes storing a virtual machine disk in a first logical unit stored on a data store; replicating the first virtual machine disk used by a first virtual machine at a second virtual machine disk stored on a second logical unit on a cloud array storage device; storing changes to the first virtual machine disk on a journal stored on the data store; periodically rolling each virtual machine disk of virtual machines on the second logical unit to a same-point-in-time using the journal and taking a snapshot of the second logical unit at the same point-in-time and sending the snapshots to a cloud storage network.

BACKGROUND

Computer data is vital to today's organizations and a significant part of protection against disasters is focused on data protection. As solid-state memory has advanced to the point where cost of memory has become a relatively insignificant factor, organizations can afford to operate with systems that store and process terabytes of data.

Conventional data protection systems include tape backup drives, for storing organizational production site data on a periodic basis. Another conventional data protection system uses data replication, by generating a copy of production site data of an organization on a secondary backup storage system, and updating the backup with changes. The backup storage system may be situated in the same physical location as the production storage system, or in a physically remote location. Data replication systems generally operate either at the application level, at the file system level, or at the data block level.

SUMMARY

In one aspect, a method includes storing a virtual machine disk in a first logical unit stored on a data store; replicating the first virtual machine disk used by a first virtual machine at a second virtual machine disk stored on a second logical unit on a cloud array storage device; storing changes to the first virtual machine disk on a journal stored on the data store; periodically rolling each virtual machine disk of virtual machines on the second logical unit to a same-point-in-time using the journal and taking a snapshot of the second logical unit at the same point-in-time and sending the snapshots to a cloud storage network.

In another aspect, an apparatus includes electronic hardware circuitry configured to store a virtual machine disk in a first logical unit stored on a data store; replicate the first virtual machine disk used by a first virtual machine at a second virtual machine disk stored on a second logical unit on a cloud array storage device; store changes to the first virtual machine disk on a journal stored on the data store; periodically roll each virtual machine disk of virtual machines on the second logical unit to a same-point-in-time using the journal and taking a snapshot of the second logical unit at the same point-in-time; and send the snapshots to a cloud storage network.

In a further aspect, an article includes a non-transitory computer-readable medium that stores computer-executable instructions. The instructions cause a machine to store a virtual machine disk in a first logical unit stored on a data store; replicate the first virtual machine disk used by a first virtual machine at a second virtual machine disk stored on a second logical unit on a cloud array storage device; store changes to the first virtual machine disk on a journal stored on the data store; periodically roll each virtual machine disk of virtual machines on the second logical unit to a same-point-in-time using the journal and taking a snapshot of the second logical unit at the same point-in-time; and send the snapshots to a cloud storage network.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an example of a data protection system.

FIG. 2 is an illustration of an example of a journal history of write transactions for a storage system.

FIG. 3 is a block diagram of an example of a system to provide data protection in a cloud environment, according to one embodiment of the disclosure.

FIG. 4 is a flowchart of an example of a process to perform data protection in a cloud environment, according to one embodiment of the disclosure.

FIG. 5 is a flowchart of an example of a process to retrieve data in a cloud environment, according to one embodiment of the disclosure.

FIG. 6 is a flowchart of an example of a process to perform disaster recovery in a cloud environment, according to one embodiment of the disclosure.

FIG. 7 is a simplified block diagram of an example of a computer on which any or part of the processes of FIGS. 4 to 6 may be implemented, according to one embodiment of the disclosure.

DETAILED DESCRIPTION

Described herein are techniques to perform data protection in a cloud environment.

The following definitions may be useful in understanding the specification and claims.

I/O REQUEST—an input/output request (sometimes referred to as an I/O or IO), which may be a read I/O request (sometimes referred to as a read request or a read) or a write I/O request (sometimes referred to as a write request or a write).

A description of journaling and some techniques associated with journaling may be described in the patent titled “METHODS AND APPARATUS FOR OPTIMAL JOURNALING FOR CONTINUOUS DATA REPLICATION” and with U.S. Pat. No. 7,516,287, which is hereby incorporated by reference.

Referring to FIG. 1, a data protection system 100 includes two sites; Site I, which is a production site, and Site II, which is a backup site or replica site. Under normal operation the production site is the source side of system 100, and the backup site is the target side of the system. The backup site is responsible for replicating production site data. Additionally, the backup site enables roll back of Site I data to an earlier pointing time, which may be used in the event of data corruption of a disaster, or alternatively in order to view or to access data from an earlier point in time.

FIG. 1 is an overview of a system for data replication of either physical or virtual logical units. Thus, one of ordinary skill in the art would appreciate that in a virtual environment a hypervisor, in one example, would consume logical units and generate a distributed file system on them such as VMWARE® VMFS®). In particular, the hypervisor generates files in the file system and exposes the files as logical units to the virtual machines (each VMDK is seen as a SCSI device by virtual hosts). In another example, the hypervisor consumes a network based file system and exposes files in the NFS as SCSI devices to virtual hosts.

During normal operations, the direction of replicate data flow goes from source side to target side. It is possible, however, for a user to reverse the direction of replicate data flow, in which case Site I starts to behave as a target backup site, and Site II starts to behave as a source production site. Such change of replication direction is referred to as a “failover”. A failover may be performed in the event of a disaster at the production site, or for other reasons. In some data architectures, Site I or Site II behaves as a production site for a portion of stored data, and behaves simultaneously as a backup site for another portion of stored data. In some data architectures, a portion of stored data is replicated to a backup site, and another portion is not.

The production site and the backup site may be remote from one another, or they may both be situated at a common site, local to one another. Local data protection has the advantage of minimizing data lag between target and source, and remote data protection has the advantage is being robust in the event that a disaster occurs at the source side.

The source and target sides communicate via a wide area network (WAN) 128, although other types of networks may be used.

Each side of system 100 includes three major components coupled via a storage area network (SAN); namely, (i) a storage system, (ii) a host computer, and (iii) a data protection appliance (DPA). Specifically with reference to FIG. 1, the source side SAN includes a source host computer 104, a source storage system 108, and a source DPA 112. Similarly, the target side SAN includes a target host computer 116, a target storage system 120, and a target DPA 124. As well, the protection agent (sometimes referred to as a splitter) may run on the host, or on the storage, or in the network or at a hypervisor level, and that DPAs are optional and DPA code may run on the storage array too, or the DPA 124 may run as a virtual machine.

Generally, a SAN includes one or more devices, referred to as “nodes”. A node in a SAN may be an “initiator” or a “target”, or both. An initiator node is a device that is able to initiate requests to one or more other devices; and a target node is a device that is able to reply to requests, such as SCSI commands, sent by an initiator node. A SAN may also include network switches, such as fiber channel switches. The communication links between each host computer and its corresponding storage system may be any appropriate medium suitable for data transfer, such as fiber communication channel links.

The host communicates with its corresponding storage system using small computer system interface (SCSI) commands.

System 100 includes source storage system 108 and target storage system 120. Each storage system includes physical storage units for storing data, such as disks or arrays of disks. Typically, storage systems 108 and 120 are target nodes. In order to enable initiators to send requests to storage system 108, storage system 108 exposes one or more logical units (LU) to which commands are issued. Thus, storage systems 108 and 120 are SAN entities that provide multiple logical units for access by multiple SAN initiators.

Logical units are a logical entity provided by a storage system, for accessing data stored in the storage system. The logical unit may be a physical logical unit or a virtual logical unit. A logical unit is identified by a unique logical unit number (LUN). Storage system 108 exposes a logical unit 136, designated as LU A, and storage system 120 exposes a logical unit 156, designated as LU B.

LU B is used for replicating LU A. As such, LU B is generated as a copy of LU A. In one example, LU B is configured so that its size is identical to the size of LU A. Thus, for LU A, storage system 120 serves as a backup for source side storage system 108. Alternatively, as mentioned hereinabove, some logical units of storage system 120 may be used to back up logical units of storage system 108, and other logical units of storage system 120 may be used for other purposes. Moreover, there is symmetric replication whereby some logical units of storage system 108 are used for replicating logical units of storage system 120, and other logical units of storage system 120 are used for replicating other logical units of storage system 108.

System 100 includes a source side host computer 104 and a target side host computer 116. A host computer may be one computer, or a plurality of computers, or a network of distributed computers, each computer may include inter alia a conventional CPU, volatile and non-volatile memory, a data bus, an I/O interface, a display interface and a network interface. Generally a host computer runs at least one data processing application, such as a database application and an e-mail server.

Generally, an operating system of a host computer generates a host device for each logical unit exposed by a storage system in the host computer SAN. A host device is a logical entity in a host computer, through which a host computer may access a logical unit. Host device 104 identifies LU A and generates a corresponding host device 140, designated as Device A, through which it can access LU A. Similarly, host computer 116 identifies LU B and generates a corresponding device 160, designated as Device B.

In the course of continuous operation, host computer 104 is a SAN initiator that issues I/O requests (write/read operations) through host device 140 to LU A using, for example, SCSI commands. Such requests are generally transmitted to LU A with an address that includes a specific device identifier, an offset within the device, and a data size. Offsets are generally aligned to 512 byte blocks. The average size of a write operation issued by host computer 104 may be, for example, 10 kilobytes (KB); i.e., 20 blocks. For an I/O rate of 50 megabytes (MB) per second, this corresponds to approximately 5,000 write transactions per second.

System 100 includes two data protection appliances, a source side DPA 112 and a target side DPA 124. A DPA performs various data protection services, such as data replication of a storage system, and journaling of I/O requests issued by a host computer to source side storage system data. As explained in detail herein, when acting as a target side DPA, a DPA may also enable roll back of data to an earlier point in time, and processing of rolled back data at the target site. Each DPA 112 and 124 is a computer that includes inter alia one or more conventional CPUs and internal memory.

For additional safety precaution, each DPA is a cluster of such computers. Use of a cluster ensures that if a DPA computer is down, then the DPA functionality switches over to another computer. The DPA computers within a DPA cluster communicate with one another using at least one communication link suitable for data transfer via fiber channel or IP based protocols, or such other transfer protocol. One computer from the DPA cluster serves as the DPA leader. The DPA cluster leader coordinates between the computers in the cluster, and may also perform other tasks that require coordination between the computers, such as load balancing.

In the architecture illustrated in FIG. 1, DPA 112 and DPA 124 are standalone devices integrated within a SAN. Alternatively, each of DPA 112 and DPA 124 may be integrated into storage system 108 and storage system 120, respectively, or integrated into host computer 104 and host computer 116, respectively. Both DPAs communicate with their respective host computers through communication lines such as fiber channels using, for example, SCSI commands or any other protocol.

DPAs 112 and 124 are configured to act as initiators in the SAN; i.e., they can issue I/O requests using, for example, SCSI commands, to access logical units on their respective storage systems. DPA 112 and DPA 124 are also configured with the necessary functionality to act as targets; i.e., to reply to I/O requests, such as SCSI commands, issued by other initiators in the SAN, including inter alia their respective host computers 104 and 116. Being target nodes, DPA 112 and DPA 124 may dynamically expose or remove one or more logical units.

As described hereinabove, Site I and Site II may each behave simultaneously as a production site and a backup site for different logical units. As such, DPA 112 and DPA 124 may each behave as a source DPA for some logical units, and as a target DPA for other logical units, at the same time.

Host computer 104 and host computer 116 include protection agents 144 and 164, respectively. Protection agents 144 and 164 intercept SCSI commands issued by their respective host computers, via host devices to logical units that are accessible to the host computers. A data protection agent may act on an intercepted SCSI commands issued to a logical unit, in one of the following ways: send the SCSI commands to its intended logical unit; redirect the SCSI command to another logical unit; split the SCSI command by sending it first to the respective DPA; after the DPA returns an acknowledgement, send the SCSI command to its intended logical unit; fail a SCSI command by returning an error return code; and delay a SCSI command by not returning an acknowledgement to the respective host computer.

A protection agent may handle different SCSI commands, differently, according to the type of the command. For example, a SCSI command inquiring about the size of a certain logical unit may be sent directly to that logical unit, while a SCSI write command may be split and sent first to a DPA associated with the agent. A protection agent may also change its behavior for handling SCSI commands, for example as a result of an instruction received from the DPA.

Specifically, the behavior of a protection agent for a certain host device generally corresponds to the behavior of its associated DPA with respect to the logical unit of the host device. When a DPA behaves as a source site DPA for a certain logical unit, then during normal course of operation, the associated protection agent splits I/O requests issued by a host computer to the host device corresponding to that logical unit. Similarly, when a DPA behaves as a target device for a certain logical unit, then during normal course of operation, the associated protection agent fails I/O requests issued by host computer to the host device corresponding to that logical unit.

Communication between protection agents and their respective DPAs may use any protocol suitable for data transfer within a SAN, such as fiber channel, or SCSI over fiber channel. The communication may be direct, or via a logical unit exposed by the DPA. Protection agents communicate with their respective DPAs by sending SCSI commands over fiber channel.

Protection agents 144 and 164 are drivers located in their respective host computers 104 and 116. Alternatively, a protection agent may also be located in a fiber channel switch, or in any other device situated in a data path between a host computer and a storage system or on the storage system itself. In a virtualized environment, the protection agent may run at the hypervisor layer or in a virtual machine providing a virtualization layer.

What follows is a detailed description of system behavior under normal production mode, and under recovery mode.

In production mode DPA 112 acts as a source site DPA for LU A. Thus, protection agent 144 is configured to act as a source side protection agent; i.e., as a splitter for host device A. Specifically, protection agent 144 replicates SCSI I/O write requests. A replicated SCSI I/O write request is sent to DPA 112. After receiving an acknowledgement from DPA 124, protection agent 144 then sends the SCSI I/O write request to LU A. After receiving a second acknowledgement from storage system 108 host computer 104 acknowledges that an I/O command complete.

When DPA 112 receives a replicated SCSI write request from data protection agent 144, DPA 112 transmits certain I/O information characterizing the write request, packaged as a “write transaction”, over WAN 128 to DPA 124 on the target side, for journaling and for incorporation within target storage system 120.

DPA 112 may send its write transactions to DPA 124 using a variety of modes of transmission, including inter alia (i) a synchronous mode, (ii) an asynchronous mode, and (iii) a snapshot mode. In synchronous mode, DPA 112 sends each write transaction to DPA 124, receives back an acknowledgement from DPA 124, and in turns sends an acknowledgement back to protection agent 144. Protection agent 144 waits until receipt of such acknowledgement before sending the SCSI write request to LU A.

In asynchronous mode, DPA 112 sends an acknowledgement to protection agent 144 upon receipt of each I/O request, before receiving an acknowledgement back from DPA 124.

In snapshot mode, DPA 112 receives several I/O requests and combines them into an aggregate “snapshot” of all write activity performed in the multiple I/O requests, and sends the snapshot to DPA 124, for journaling and for incorporation in target storage system 120. In snapshot mode DPA 112 also sends an acknowledgement to protection agent 144 upon receipt of each I/O request, before receiving an acknowledgement back from DPA 124.

For the sake of clarity, the ensuing discussion assumes that information is transmitted at write-by-write granularity.

While in production mode, DPA 124 receives replicated data of LU A from DPA 112, and performs journaling and writing to storage system 120. When applying write operations to storage system 120, DPA 124 acts as an initiator, and sends SCSI commands to LU B.

During a recovery mode, DPA 124 undoes the write transactions in the journal, so as to restore storage system 120 to the state it was at, at an earlier time.

As described hereinabove, LU B is used as a backup of LU A. As such, during normal production mode, while data written to LU A by host computer 104 is replicated from LU A to LU B, host computer 116 should not be sending I/O requests to LU B. To prevent such I/O requests from being sent, protection agent 164 acts as a target site protection agent for host Device B and fails I/O requests sent from host computer 116 to LU B through host Device B.

Target storage system 120 exposes a logical unit 176, referred to as a “journal LU”, for maintaining a history of write transactions made to LU B, referred to as a “journal”. Alternatively, journal LU 176 may be striped over several logical units, or may reside within all of or a portion of another logical unit. DPA 124 includes a journal processor 180 for managing the journal.

Journal processor 180 functions generally to manage the journal entries of LU B. Specifically, journal processor 180 enters write transactions received by DPA 124 from DPA 112 into the journal, by writing them into the journal LU, reads the undo information for the transaction from LU B. updates the journal entries in the journal LU with undo information, applies the journal transactions to LU B, and removes already-applied transactions from the journal.

Referring to FIG. 2, which is an illustration of a write transaction 200 for a journal. The journal may be used to provide an adaptor for access to storage 120 at the state it was in at any specified point in time. Since the journal includes the “undo” information necessary to roll back storage system 120, data that was stored in specific memory locations at the specified point in time may be obtained by undoing write transactions that occurred subsequent to such point in time.

Write transaction 200 generally includes the following fields: one or more identifiers; a time stamp, which is the date & time at which the transaction was received by source side DPA 112; a write size, which is the size of the data block; a location in journal LU 176 where the data is entered; a location in LU B where the data is to be written; and the data itself.

Write transaction 200 is transmitted from source side DPA 112 to target side DPA 124. As shown in FIG. 2, DPA 124 records the write transaction 200 in the journal that includes four streams. A first stream, referred to as a DO stream, includes new data for writing in LU B. A second stream, referred to as an DO METADATA stream, includes metadata for the write transaction, such as an identifier, a date & time, a write size, a beginning address in LU B for writing the new data in, and a pointer to the offset in the DO stream where the corresponding data is located. Similarly, a third stream, referred to as an UNDO stream, includes old data that was overwritten in LU B; and a fourth stream, referred to as an UNDO METADATA, include an identifier, a date & time, a write size, a beginning address in LU B where data was to be overwritten, and a pointer to the offset in the UNDO stream where the corresponding old data is located.

In practice each of the four streams holds a plurality of write transaction data. As write transactions are received dynamically by target DPA 124, they are recorded at the end of the DO stream and the end of the DO METADATA stream, prior to committing the transaction. During transaction application, when the various write transactions are applied to LU B, prior to writing the new DO data into addresses within the storage system, the older data currently located in such addresses is recorded into the UNDO stream. In some examples, the metadata stream (e.g., UNDO METADATA stream or the DO METADATA stream) and the data stream (e.g., UNDO stream or DO stream) may be kept in a single stream each (i.e., one UNDO data and UNDO METADATA stream and one DO data and DO METADATA stream) by interleaving the metadata into the data stream.

Referring to FIG. 3, the point-in-time CDP described in FIGS. 1 and 2 may be extended to a cloud environment, according to one embodiment of the disclosure. In one example, a system 300 includes a host 302 a, a host 302 b, a cloud storage network 304, a cloud storage device 306 and a local data store 316.

The host 302 a includes a first virtual machine (VM) 322 a, a second virtual machine 322 b, a splitter 311 and a virtual data protection appliance (vDPA) 314. The host 302 b includes a splitter 355 and a replica of the first VM 372.

The local data store includes a logical unit (LU) 324 having a file system 325 (e.g., VMWARE® VMFS®) exposing a virtual machine disk 328 a and a virtual machine disk 328 b and a LU 326 having a file system 327 exposing a virtual machine disk 329 used for a journal (also called herein journal 329). In one particular example, the journal 329 is similar to a four stream journal (e.g., journal 176 described in FIGS. 1 and 2).

The cloud storage array device 306 includes a LU 338 having a file system 331 (e.g., VMWARE® VMFS®) exposing a virtual machine virtual machine disk 333 which is the replica of virtual machine disk 328 a. The cloud storage array device 306 stores a portion of the cloud storage. For example, if the cloud storage is allocated 1 TB of storage only 10 GB is on the cloud storage array device 306 and the rest is on the cloud storage network 304, i.e. the cloud storage array device 306 serves as a cache for cloud storage data 348.

The cloud storage network 304 includes snapshots 342 of the virtual machine disk 333 and volume data 348 of the cloud storage device 306. The snapshots 342 include a snapshot 343, which is a snapshot of the LU 338.

The first virtual machine 322 a uses virtual machine disk 328 a as storage. The second virtual machine 322 b uses virtual machine disk 328 b for storage. In one example, the virtual machine disk 328 a is replicated to the virtual machine disk 333 of the cloud storage device 306 and the virtual machine disk 328 b is not replicated as virtual machine 322 b is not replicated.

In most embodiments, the cloud storage network 304 is an object-based storage stored in a cloud (e.g., AMAZON S3 or any other object-based cloud storage). In one example, the cloud storage array device 306 may be, for example, EMC® CLOUDARRAY®.

Referring to FIG. 4, a process 400 is an example of a process to perform data protection in a cloud environment, according to one embodiment of the disclosure. Process 400 performs data protection locally (402). For example, a replica of the virtual machine disk 328 a is taken and stored with the virtual machine disk 333 and subsequent changes to the virtual machine disk 328 a are stored on the journal 329.

Process 400 periodically takes a consistent snapshot of a logical unit containing storage for the virtual machines (406). For example, the snapshot 343 is taken of LU 338 at a consistent point-in-time. The cloud storage array device 306 exposes an LU, and copies of the full LU are stored in the object store in the cloud storage array network 304 as snapshots 342. In order to get a consistent view of the disk of the virtual machines stored in LU 338, each of the data stored in the disks are rolled to the same consistent point-in-time using the journal 329 and only then when the data of the virtual machines is paused on a consistent point-in-time a snapshot of LU 338 is taken.

Process 400 sends the snapshot of the logical unit to the cloud storage network (408). For example, the cloud storage array device 306 sends the snapshot to the cloud storage network 304 to be stored with the snapshots 342.

Referring to FIG. 5, a process 500 is an example of a process to retrieve data in a cloud environment, according to one embodiment of the disclosure. Process 500 presents available point-in-time to restore (502). For example, system 300 renders (e.g., using a UI 708 (FIG. 7)) available points-in-time to restore. Process 506 receives a selected time to restore (506). For example, a user (using the UI 708 (FIG. 7) selects a point-in-time to restore.

Process 500 determines if the data for the selected time is on the journal (510). For example, the journal 329 saves data no longer than a day. If the selected time is greater than one day, then the data is not saved on the journal 329.

If the data is saved on the journal 329, process 500 performs a roll back locally using the journal 329 (516). For example, the system 300 rolls back to the selected point-in-time using the processes described in FIGS. 1 and 2. In one example, the journal 329 is used to roll back the virtual machine disk 333.

If the data is not saved on the journal 329, process 500 retrieves the snapshot of the VMs from the cloud storage network 304 for the selected time (520). For example, a point-in-time snapshot (e.g., snapshot 343) of LU 338, is exposed to hosts 302 a, 302 b, the file system 331 is mounted on the snapshot (e.g., snapshot 343), and a virtual machine is configured to use the copy of the data in the newly exposed file system. In one example, if the data requested is not in the journal then a few selected snapshots that are stored in the cloud storage network are available, but not any point-in-time snapshot as the journal allows.

Referring to FIG. 6, a process 600 is an example of a process to perform disaster recovery, according to one embodiment of the disclosure. Process 600 receives a notification of a disaster (602) For example, a production site is lost, and a new production site is generated, and receives notification of a new host (608). For example, a new ESX host (not shown) is configured in the new site.

Process 600 deploys new cloud storage array device (614) and restores configuration of the cloud array storage device (618). For example, a new cloud array storage device (not shown) is configured using to use the cloud storage network 304 and retrieve the volume data 348 and its snapshot copies.

Process 600 exposes a snapshot from cloud network (622) and mounts the snapshot to the new host (626). For example, the latest snapshot from the snapshots 342 is exposed and is mounted by the new host.

Process 600 forms new data store (636). For example, a new data store is formed on the new cloud storage array device.

Process 600 imports virtual machines (638). For example, the virtual machines are imported from the newly created data store. In one example, since cloud data store performance may be poor, a storage mechanism (e.g., VMWARE® STORAGE VMOTION™) or any other copy mechanism may be used to move data into a production data store on new host. In one example, the copy mechanism is performed automatically without user intervention.

Referring to FIG. 7, in one example, a computer 700 includes a processor 702, a volatile memory 704, a non-volatile memory 706 (e.g., hard disk) and the user interface (UI) 708 (e.g., a graphical user interface, a mouse, a keyboard, a display, touch screen and so forth). The non-volatile memory 706 stores computer instructions 712, an operating system 716 and data 718. In one example, the computer instructions 712 are executed by the processor 702 out of volatile memory 704 to perform all or part of the processes described herein (e.g., processes 400, 500 and 600).

The processes described herein (e.g., processes 400, 500 and 600) are not limited to use with the hardware and software of FIG. 7; they may find applicability in any computing or processing environment and with any type of machine or set of machines that is capable of running a computer program. The processes described herein may be implemented in hardware, software, or a combination of the two. The processes described herein may be implemented in computer programs executed on programmable computers/machines that each includes a processor, a non-transitory machine-readable medium or other article of manufacture that is readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and one or more output devices. Program code may be applied to data entered using an input device to perform any of the processes described herein and to generate output information.

The system may be implemented, at least in part, via a computer program product, (e.g., in a non-transitory machine-readable storage medium such as, for example, a non-transitory computer-readable medium), for execution by, or to control the operation of, data processing apparatus (e.g., a programmable processor, a computer, or multiple computers). Each such program may be implemented in a high level procedural or object-oriented programming language to communicate with a computer system. However, the programs may be implemented in assembly or machine language. The language may be a compiled or an interpreted language and it may be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program may be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network. A computer program may be stored on a non-transitory machine-readable medium that is readable by a general or special purpose programmable computer for configuring and operating the computer when the non-transitory machine-readable medium is read by the computer to perform the processes described herein. For example, the processes described herein may also be implemented as a non-transitory machine-readable storage medium, configured with a computer program, where upon execution, instructions in the computer program cause the computer to operate in accordance with the processes. A non-transitory machine-readable medium may include but is not limited to a hard drive, compact disc, flash memory, non-volatile memory, volatile memory, magnetic diskette and so forth but does not include a transitory signal per se.

The processes described herein are not limited to the specific examples described. For example, the processes 400, 500 and 600 are not limited to the specific processing order of FIGS. 4 to 6, respectively. Rather, any of the processing blocks of FIGS. 4 to 6 may be re-ordered, combined or removed, performed in parallel or in serial, as necessary, to achieve the results set forth above.

The processing blocks (for example, in the processes 400, 500 and 600) associated with implementing the system may be performed by one or more programmable processors executing one or more computer programs to perform the functions of the system. All or part of the system may be implemented as, special purpose logic circuitry (e.g., an FPGA (field-programmable gate array) and/or an ASIC (application-specific integrated circuit)). All or part of the system may be implemented using electronic hardware circuitry that include electronic devices such as, for example, at least one of a processor, a memory, a programmable logic device or a logic gate.

Elements of different embodiments described herein may be combined to form other embodiments not specifically set forth above. Various elements, which are described in the context of a single embodiment, may also be provided separately or in any suitable subcombination. Other embodiments not specifically described herein are also within the scope of the following claims. 

What is claimed is:
 1. A method comprising: storing a first virtual machine disk in a first logical unit stored on a data store; replicating the first virtual machine disk used by a first virtual machine at a second virtual machine disk stored on a second logical unit on a cloud array storage device; storing changes to the first virtual machine disk on a journal stored on the data store wherein the journal comprises; a first stream corresponding to new data written to the first virtual machine disk; a second stream corresponding to metadata associated with write transactions to the first virtual machine disk; a third stream corresponding to old data overwritten on the first virtual machine disk; and a fourth stream corresponding to a date and time, a write size, and a beginning address associated with old overwritten data; periodically rolling each virtual machine disk of virtual machines on the second logical unit to a same-point-in-time using the journal and taking a snapshot of the second logical unit at the same point-in-time; and sending the snapshots to a cloud storage network.
 2. The method of claim 1, further comprising: receiving a request to retrieve data from a selected point-in-time; determining if data for the selected point-in-time is in the journal; rolling back the data to the selected point-in-time using the journal if the data for the selected point-in-time is on the journal; and retrieving a snapshot from the selected point-in-time from the cloud storage network if the data for the selected point-in-time is not on the journal.
 3. The method of claim 2, wherein if the data for the selected point-in-time is not on the journal, the retrieving the snapshot from the cloud storage network comprises: exposing the snapshot to a host; mounting a file system; and configuring the first virtual machine.
 4. The method of claim 1, further comprising: receiving notification of a disaster; receiving notification of a new host; deploying a new cloud storage device; restoring configurations of an old cloud storage device to the new cloud storage device; exposing a snapshot of the second logical unit; allowing the new host to mount the snapshot of the second logical unit; forming a new data store on the new cloud storage device; and importing the virtual machines on to the new cloud storage device.
 5. The method of claim 4, wherein importing the virtual machines comprises importing the virtual machines from the data store using a copy mechanism.
 6. An apparatus, comprising: electronic hardware circuitry configured to: store a first virtual machine disk in a first logical unit stored on a data store; replicate the first virtual machine disk used by a first virtual machine at a second virtual machine disk stored on a second logical unit on a cloud array storage device; store changes to the first virtual machine disk on a journal stored on the data store, wherein the journal comprises; a first stream corresponding to new data written to the first virtual machine disk; a second stream corresponding to metadata associated with write transactions to the first virtual machine disk; a third stream corresponding to old data overwritten on the first virtual machine disk; and a fourth stream corresponding to a date and time, a write size, and a beginning address associated with old overwritten data; periodically roll each virtual machine disk of virtual machines on the second logical unit to a same-point-in-time using the journal and taking a snapshot of the second logical unit at the same point-in-time; and send the snapshots to a cloud storage network.
 7. The apparatus of claim 6, wherein the circuitry comprises at least one of a processor, a memory, a programmable logic device or a logic gate.
 8. The apparatus of claim 6, further comprising circuitry configured to: receive a request to retrieve data from a selected point-in-time; determine if data for the selected point-in-time is in the journal; roll back the data to the selected point-in-time using the journal if the data for the selected point-in-time is on the journal; and retrieve a snapshot from the selected point-in-time from the cloud storage network if the data for the selected point-in-time is not on the journal.
 9. The apparatus of claim 8, wherein circuitry configured to retrieve the snapshot from the cloud storage network if the data for the selected point-in-time is not on the journal comprises circuitry configured to: expose the snapshot to a host; mount a file system; and configure the first virtual machine.
 10. The apparatus of claim 6, further comprising circuitry configured to: receive notification of a disaster; receive notification of a new host; deploy a new cloud storage device; restore configurations of an old cloud storage device to the new cloud storage device; expose a snapshot of the second logical unit; allow the new host to mount the snapshot of the second logical unit; form a new data store on the new cloud storage device; and import the virtual machines on to the new cloud storage device.
 11. The apparatus of claim 10, wherein the circuitry configured to import the virtual machines comprises circuitry configured to import the virtual machines from the data store using a copy mechanism.
 12. An article comprising: a non-transitory computer-readable medium that stores computer-executable instructions, the instructions causing a machine to: store a first virtual machine disk in a first logical unit stored on a data store; replicate the first virtual machine disk used by a first virtual machine at a second virtual machine disk stored on a second logical unit on a cloud array storage device; store changes to the first virtual machine disk on a journal stored on the data store wherein the journal comprises; a first stream corresponding to new data written to the first virtual machine disk: a second stream corresponding to metadata associated with write transactions to the first virtual machine disk; a third stream corresponding to old data overwritten on the first virtual machine disk; and a fourth stream corresponding to a date and time, a write size, and a beginning address associated with old overwritten data; periodically roll each virtual machine disk of virtual machines on the second logical unit to a same-point-in-time using the journal and taking a snapshot of the second logical unit at the same point-in-time; and send the snapshots to a cloud storage network.
 13. The article of claim 12, further comprising instructions causing the machine to: receive a request to retrieve data from a selected point-in-time; determine if data for the selected point-in-time is in the journal; roll back the data to the selected point-in-time using the journal if the data for the selected point-in-time is on the journal; and retrieve a snapshot from the selected point-in-time from the cloud storage network if the data for the selected point-in-time is not on the journal.
 14. The article of claim 13, wherein instructions causing the machine to retrieve the snapshot from the cloud storage network if the data for the selected point-in-time is not on the journal comprises instructions causing the machine to: expose the snapshot to a host; mount a file system; and configure the first virtual machine.
 15. The article of claim 12, further comprising instructions causing the machine to: receive notification of a disaster; receive notification of a new host; deploy a new cloud storage device; restore configurations of an old cloud storage device to the new cloud storage device; expose a snapshot of the second logical unit; allow the new host to mount the snapshot of the second logical unit; form a new data store on the new cloud storage device; and import the virtual machines on to the new cloud storage device.
 16. The article of claim 15, wherein the instructions causing the machine to import the virtual machines comprises instructions causing the machine to import the virtual machines from the data store using a copy mechanism. 